Revert #169: park claude-set-token + dev-env OAuth activation#170
Merged
lmoresi merged 1 commit intodevelopmentfrom May 5, 2026
Merged
Revert #169: park claude-set-token + dev-env OAuth activation#170lmoresi merged 1 commit intodevelopmentfrom
lmoresi merged 1 commit intodevelopmentfrom
Conversation
Reverts the changes introduced by PR #169 (`uw: add claude-set-token subcommand + dev-env activation for OAuth token`). The feature over-promised relative to what Claude Code 2.x actually does with the OAuth env var: CLAUDE_CODE_OAUTH_TOKEN is honoured only in non-interactive mode (`claude -p "..."` and scripted use). Bare/interactive `claude` always tries browser auth first regardless. So on a truly headless remote, our `./uw shell` + persisted token flow still results in a browser-login prompt the user can't service. The subcommand and its --help advertised a workflow that doesn't quite work and was therefore potentially misleading. What this revert removes: - ./uw claude-set-token subcommand and its --help block - claude-set-token entry in ./uw --help Setup section - [feature.dev.activation] block in pixi.toml - scripts/activate-claude-auth.sh What stays (still earn their keep regardless of this auth quirk): - ./uw install-claude (PR #167) - ./uw shell (PR #168) If a useful headless-auth workflow appears later (e.g. an ANTHROPIC_API_KEY-based path for interactive use that Pro/Max users are willing to pay for), this can be revisited with honest documentation about which mode it serves. Underworld development team with AI support from Claude Code (https://claude.com/claude-code)
Contributor
There was a problem hiding this comment.
Pull request overview
This PR cleanly reverts the recently added Claude OAuth convenience flow from the repository’s uw environment wrapper and dev pixi environment. In the broader codebase, it narrows the developer tooling back to the supported install-claude, claude-perms, and ./uw shell flows after the reverted feature proved misleading for headless interactive use.
Changes:
- Removes the
./uw claude-set-tokensubcommand implementation, help text, and command dispatch fromuw. - Removes the
claude-set-tokenentry from./uw --help. - Removes the dev-environment activation hook from
pixi.tomland deletes the supportingscripts/activate-claude-auth.shscript.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
uw |
Removes the reverted CLI subcommand, its help block, and its command registration. |
scripts/activate-claude-auth.sh |
Deletes the token-export activation script introduced by the reverted feature. |
pixi.toml |
Removes the dev feature activation stanza that sourced the deleted auth script. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reverts PR #169 (
uw: add claude-set-token subcommand + dev-env activation for OAuth token).After live-testing on a headless remote (hyperion), the feature turned out to over-promise relative to what Claude Code 2.x actually does with the OAuth env var:
So on a truly headless box, our
./uw claude-set-token→./uw shell→claudeflow still results in a browser-login prompt the user can't service. The subcommand and its--helpadvertised a workflow that doesn't quite work, and was therefore potentially misleading. There is no current way to use Pro/Max OAuth for interactive Claude Code on a headless machine — the only options areclaude -p(works with our env-var setup but loses the interactive REPL) orANTHROPIC_API_KEY(works but routes through metered API credits, not subscription).What this removes
./uw claude-set-tokensubcommand + its--helpblockclaude-set-tokenline in./uw --helpSetup section[feature.dev.activation]block inpixi.tomlscripts/activate-claude-auth.shWhat stays (unaffected)
./uw install-claude(PR uw: prompt to install Claude Code CLI during dev setup #167) — installing the binary still earns its keep../uw shell(PR uw: add./uw shell, warn about barepixi shellafter setup #168) — independent of auth, just opens the configured pixi env.Test plan
bash -n uwclean (verified locally)claude-set-tokenoractivate-claude-authinuworpixi.tomlscripts/activate-claude-auth.shremoved./uw --helpno longer listsclaude-set-tokenFuture
If a useful headless-auth workflow appears later (e.g. an
ANTHROPIC_API_KEY-based path for interactive use that Pro/Max users are willing to pay for, or upstream Claude Code starts honouring the OAuth token in interactive mode), this can be revisited with honest documentation about which mode it serves.Underworld development team with AI support from Claude Code